doc: clarify callback exceptions#63939
Merged
nodejs-github-bot merged 1 commit intoJun 18, 2026
Merged
Conversation
Signed-off-by: Matteo Collina <hello@matteocollina.com>
Collaborator
|
Review requested:
|
panva
approved these changes
Jun 16, 2026
aduh95
approved these changes
Jun 16, 2026
aduh95
added
author ready
watilde
approved these changes
Jun 16, 2026
trivikr
approved these changes
Jun 16, 2026
lpinca
approved these changes
Jun 16, 2026
legendecas
approved these changes
Jun 17, 2026
nodejs-github-bot
removed
the
commit-queue
Collaborator
|
Landed in 4e7c07d |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
8 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This updates the security policy to clarify that crashes caused by application callbacks throwing uncaught exceptions are outside the Node.js threat model.
It also points to CVE-2026-21637 as an example of a case that was previously triaged as a vulnerability but should not be treated as one going forward.
Fixes: nodejs/security-wg#1568